Use the following case-sensitive format to name Process Setup Option (PSO) columns.
<Process Name>:<Option Name>#<Mode Name>
The #Mode Name# entry is optional, and the default value for mode name is user
The available options vary from cost model to cost model - here are some example PSOs.
Option Name | Purpose | Example column heading |
|---|---|---|
includeOptionalRouting | Selects an optional process | Wet Coat Line:includeOptionalRouting |
machine | Selects the machine for a specific process | 3 Axis Mill:machine |
digital factory | Selects an XPG Digital Factory |
CSL Formula Override columns (non-custom processes only)
Like PSO columns, CSL Formula Override column names begin with
<Process Name>:
The heading has the format of <Process Name>:override.<Formula Name>. The data type of override values is Double.
Note: CSL overrides in bulk costing are subject to the same limitations as in the main aPriori UI. See Override Computed Values.
Custom (defined) Attribute columns
Add additional columns to your input spreadsheet for any User Defined Attributes (UDAs) using the format: customAttributes.<Name>
For example, to add a UDA with the name CreationDate, create a column titled: customAttributes.CreationDate in your spreadsheet.
See Managing user defined attributes for more information on the creation and management of user attributes.
Ensure your UDA column names exactly match the Name (not Display Name) of the UDA.